|
Author |
Thread Statistics | Show CCP posts - 5 post(s) |

Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.06 14:43:00 -
[1]
Originally by: Konoch
Originally by: Lupus Aurelius You promote major fleet battles as a selling point to EVE, yet do not actually have the capablity to support them, and based on TZ and who loads more ships into a system, they can lag it so badly that NO ONE, no matter who it is, can do anything about it.
HERE HERE! I've been calling for exactly the same goddamned thing. People are lucky i'm not a GM in this game or i'd have torn alliances apart for this.
So why don't the defenders get themselves in to the system before the attackers? I guess one side is more dedicated than the other...
|

Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.07 06:54:00 -
[2]
Originally by: Batolemaeus Did it ever occur to you that defenders are the ones that react to what the attackers are doing? So they naturally are the ones who are late?
I know this is a very challenging thing for you to grasp, but in warfare it's usually the attacker who knows where to strike first.
Oh, I see. Thank you for correcting my ignorance on how 0.0 sovereignty battles work. With this newfound knowledge I can properly appreciate the magnificent exploits of MM. 
Not a single detail, no matter how small or insignificant, will ever again escape my notice again. Thank you, wise Batolemaeus, for the knowledge you have imparted upon me.
|

Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.09 01:19:00 -
[3]
Originally by: Zenst
Originally by: CCP Atlas
Originally by: BlackHorizon ...from what I can read from CCP Atlas' posts, CCP forced the node to stay online.
That is actually not what happened. A bug which caused nodes to die was fixed. It is as simple as that.
When you say `fixed` (fixed, fixed) do you mean:
Your dictionary-fu is strong, but not really applicable.
As mentioned in the dev post; they had a heartbeat timer that wasn't getting sent when it should have. The 'admin faint'-inducing stuff done on the live server was likely either generating fake heartbeats, disabling them for that node or applying untested patches without the usual QA.
So CVA got ****ed by a bug fix that will go live on the rest of the cluster tomorrow. Your anus'es got stretched cause you hoped to take advantage of a bug that would make the node crash yet somehow it didn't. And now you're all butthurt about it.
Where have I heard this before? Oh, yeah... think GS/PL did something similar in... err... what system was that again.
|

Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.09 02:48:00 -
[4]
Originally by: Batolemaeus
Originally by: CCP Atlas
Originally by: BlackHorizon ...from what I can read from CCP Atlas' posts, CCP forced the node to stay online.
That is actually not what happened. A bug which caused nodes to die was fixed. It is as simple as that.
Nice Backpedaling.
Backpedaling or not; those of us willing to read what CCP writes now know same fix will be deployed for the whole cluster.
No doubt next weekend someone is going to post a rage thread in CAOD about how the node didn't crash at 1600 players.
|

Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.10 04:34:00 -
[5]
Originally by: Skaarl you have noticed that CCP atlas has been changing his blog and walking his comments back from "we took measures that would make a system admin faint" to "oh it was just a bug fix, we didnt actually do anything..."
What makes system admins faint is the prospect of a cluster-wide crash due to a renegade node. They don't give rats ass about your Good Fights in a 1600+ fight.
But go ahead, be all butthurt and emoraging about losing a dread. Besides, where does CCP state that a ship that logs out on a lagged node is guaranteed to be gone after 15 minutes?
|

Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.10 05:03:00 -
[6]
Originally by: evsNOTeve
Originally by: Rakshasa Taisab where does CCP state that a ship that logs out on a lagged node is guaranteed to be gone after 15 minutes?
here you go from the official evelopedia even (link is on the bar to the left here)
   
Sorry, can't see anything about lagged nodes.
Perhaps you are confused, and think CCP has guaranteed game mechanics function without lag on overloaded servers. Kinda like how our guns are supposed to work immediately when we click the little gun icon thingie even with 1000 ships on grid. 
|

Rakshasa Taisab
Caldari Sane Industries Inc. Initiative Mercenaries
|
Posted - 2010.02.10 05:37:00 -
[7]
Originally by: evsNOTeve no but it doesnt say that it doesnt work on a lagged node either.....
are you really that dense? the 1min/15min timers have been in the game A LONG time, and it for sure should be one thing that works on a node, lagged or not (it helps the server to know that it doesn't have to worry about that ship anymore....)
Now you are projecting your own expectations on what you think _should_ happen, and making it the official rules.
CCP has never claimed that using the ship scanner doesn't work on a lagged node either...
Or that ejecting Exotic Dancers won't get lagged, or what ever.
|
|
|
|